Thread-specific event management in a non-stop debugging environment

ABSTRACT

A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee. In the non-stop debugging environment, encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of the other threads. Thread-specific events may managed in the non-stop debug environment by identifying, by the debugger for a thread of execution of the debuggee not currently executing, a thread-specific event associated with the thread; removing, by the debugger, the thread-specific event for all threads of the debuggee; and upon the thread resuming execution, replacing, by the debugger, the thread-specific event.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of and claims priorityfrom U.S. patent application Ser. No. 13/033,925, filed on Feb. 24,2011.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, apparatus, and products for thread-specific event management ina non-stop debugging environment.

2. Description of Related Art

Software source code is increasingly complex and execution of suchsoftware may be multi-threaded. Software development is evolving toprovide enhanced methods of debugging multi-threaded softwareapplications. In traditional debugging, an event encountered by any onethread stops execution of all threads of the multi-threaded solution.This form of debugging may be referred to as ‘all-stop’ debugging. incontrast to all-stop debugging, the enhanced multi-threaded debuggingenables an event encountered by one thread to stop only that onethread's execution while all other threads remain executing. This formof debugging is referred to as non-stop debugging. Non-stop debugging isa bit of a misnomer, however, in that some threads actually do stopexecution. The primary difference between non-stop and all stopdebugging, is that in non-stop debugging execution of all threads of amulti-threaded program need not be stopped upon a single threadencountering an event, while in all-stop debugging execution of allthreads is stopped upon a single thread of the multi-threadedapplication encountering an event. While non-stop debugging providesmany benefits, non-stop debugging also presents many challenges.

SUMMARY OF THE INVENTION

Methods, apparatus, and products for thread-specific event management ina non-stop debugging environment are disclosed. The non-stop debuggingenvironment includes a debugger configured to debug a debuggee that, inturn, includes a plurality of threads of execution. In the non-stopdebugging environment, encountering an event by one of the threads stopsexecution of only the one thread without concurrently stopping executionof the other threads. Thread-specific event management in the non-stopdebugging environment in accordance with embodiments of the presentinvention includes, identifying, by the debugger for a thread ofexecution of the debuggee not currently executing, a thread-specificevent associated with the thread; removing, by the debugger, thethread-specific event for all threads of the debuggee; and, upon thethread resuming execution, replacing, by the debugger, thethread-specific event.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of a system for thread-specific eventmanagement in a non-stop debugging environment according to embodimentsof the present invention.

FIG. 2 sets forth an example non-stop debugging GUI presented to a userin accordance with embodiments of the present invention.

FIG. 3 sets forth a flow chart illustrating an exemplary method forthread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 4 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 5 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 6 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 7 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 8 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

FIG. 9 sets forth a flow chart illustrating a further exemplary methodfor thread-specific event management in a non-stop debugging environmentaccording to embodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary methods, apparatus, and products for thread-specific eventmanagement in a non-stop debugging environment in accordance with thepresent invention are described with reference to the accompanyingdrawings, beginning with FIG. 1. FIG. 1 sets forth a block diagram of asystem for thread-specific event management in a non-stop debuggingenvironment according to embodiments of the present invention. Thesystem of FIG. 1 includes automated computing machinery comprising anexemplary computer (152) useful in thread-specific event management in anon-stop debugging environment according to embodiments of the presentinvention. The computer (152) of FIG. 1 includes at least one computerprocessor (156) or ‘CPU’ as well as random access memory (168) (‘RAM’)which is connected through a high speed memory bus (166) and bus adapter(158) to processor (156) and to other components of the computer (152).

Stored in RAM (168) are a debugger (126) and a debuggee (120). Adebugger (126) is an application that controls operation of anotherapplication—the debuggee (120)—for the purpose of testing execution ofthe debuggee. The source code of the debuggee may run on an instructionset simulator (ISS), a technique that allows great power in its abilityto halt when specific conditions are encountered but which willtypically be somewhat slower than executing the code directly on aprocessor for which the code is written. When execution of a programcrashes or reaches a preset condition, a debugger typically displays theposition in the source code at which the execution of the programcrashed. A ‘crash’ occurs when the program cannot normally continuebecause of a programming bug. In addition to displaying a position insource code when execution of the source code crashes, debuggers alsooften offer other functions such as running a program step by step(single-stepping or program animation), stopping, breaking, or pausingthe program to examine the current state, at some event or specifiedinstruction by means of a breakpoint, and tracking the values of somevariables.

In the example system of FIG. 1, the debugger (126) presents a graphicaluser interface (124) as a front-end of the debugger (126). Front-endsare extensions to debugger engines that provide Integrated DevelopmentEnvironment (‘IDE’) integration, program animation, and visualizationfeatures, rather than console-based command line interfaces. The‘front-end’ directly faces a client—or user—in contrast to the debugger(126) in the example of FIG. 1, which interfaces indirectly with theclients through the GUI (126).

In the example system of FIG. 1, the debuggee (120) is a softwareapplication that executes as a process containing a number of threads(122) of execution. A ‘thread’ of execution as the term is used hererefers to the smallest unit of processing that can be scheduled by anoperating system. A thread generally results from a fork of a computerprogram into two or more concurrently running threads. Theimplementation of threads and processes differs from one operatingsystem to another, but in most cases, a thread is contained inside aprocess. Multiple threads can exist within the same process and shareresources such as memory, while different processes do not share theseresources. In particular, the threads of a process share the process'scomputer program instructions and its context—the values that theprocess's variables reference at any given moment.

The system of FIG. 1 includes a non-stop debugging environment thatincludes the debugger (126) and the debuggee (120). The debuggersupports non-stop debugging by insuring that when one thread of amulti-threaded debuggee encounters an event, execution of only that oneof threads stops, without concurrently stopping execution of otherthreads. Consider, for example, a multi-threaded debuggee that includesthree threads. In a non-stop debug environment, when one of the threadsencounters an event, execution of that thread is stopped, but executionof the remaining two threads continues unabated. Either of other twothreads may then separately encounter an event, stopping execution ofthat thread, but no other thread. By contrast, a traditional all-stopdebugging environment insures that all threads are stopped concurrentlywith any one thread encountering an event. Continuing with the aboveexample of a triple threaded debuggee, when any one of the three threadsencounters an event in a traditional all-stop debug environment, allthree threads halt execution.

An event is a predefined occurrence during execution of a debuggee.Examples of events which may be encountered during execution of thedebuggee include breakpoints, watchpoints, catchpoints, and the like. Abreakpoint is a specification of a source code location at which adebuggee will pause or stop execution. A watchpoint is a breakpointconfigured to pause or stop execution of the debuggee when a value of aparticular expression changes. A catchpoint is another type ofbreakpoint configured to pause or stop execution of the debuggee when aspecified event occurs such as the throwing of an exception or a load ofa library, and so on.

In addition to supporting non-stop debugging generally, the debugger(126) in the example of FIG. 1 is also configured for thread-specificevent management in a non-stop debugging environment in accordance withembodiments of the present invention. Thread-specific event managementin accordance with embodiments of the present invention includesidentifying, by the debugger (126) for a thread of execution of thedebuggee (120) not currently executing, a thread-specific event (130)associated with the thread; removing, by the debugger (126), thethread-specific event for all threads (122) of the debuggee (120); and,upon the thread resuming execution, replacing, by the debugger (126),the thread-specific event (130).

A thread may stop execution for various reasons. A thread, for example,may encounter an event—thread-specific or otherwise, be in a wait state,or be stopped at the behest of a user. A thread may be in a wait statefor various reasons including for example, waiting on a lock restrictingaccess to a resource to become available, waiting on an I/O activity tocomplete, or for other reasons as will occur to readers of skill in theart.

A thread-specific event is an event—a breakpoint, watchpoint, catchpointor the like—associated with a particular, specified thread. By contrast,consider that non-thread-specific events are not associated with any onethread. Instead, a non-thread-specific event is applied to and processedfor all threads in the same manner. Further, a thread-specific event mayalso be configured such that the debugger (126) ignores an encounter ofthe event except for encounters by the thread associated with thethread-specific event. The debugger may ‘ignore’ an encounter of anevent by a thread, by immediately resuming execution of that thread.Consider, for example, two threads: Thread_1 and Thread_2. Considerfurther that Thread_1 is associated with a breakpoint at line 23. Thedebugger may, upon discovering that Thread_2 encountered the breakpointat line 23, determine that the breakpoint is a thread-specificbreakpoint associated with Thread_1 and immediately resume execution ofThread_2. From a user's perspective, then, the encounter of thebreakpoint at line 23 by Thread_2 never occurred.

In the example of FIG. 1, the thread-specific event (130) associatedwith thread (312) not currently executing is represented by an eventidentifier (132) associated with a thread identifier (134). In otherembodiments, the debugger (126) may maintain a table or other datastructure including a plurality of records, each of which represents athread-specific event and is implemented with an association of a threadidentifier and an event identifier.

Also stored in RAM (168) is an operating system (154). Operating systemsuseful in computer systems that support thread-specific event managementin a non-stop debugging environment according to embodiments of thepresent invention include UNIX™ Linux™ Microsoft XP™ AIX™ IBM's i^(TM),and others as will occur to those of skill in the art. The operatingsystem (154), debugger (126), debuggee (126), and GUI (124) in theexample of FIG. 1 are shown in RAM (168), but many components of suchsoftware typically are stored in non-volatile memory also, such as, forexample, on a disk drive (170).

The computer (152) of FIG. 1 includes disk drive adapter (172) coupledthrough expansion bus (160) and bus adapter (158) to processor (156) andother components of the computer (152). Disk drive adapter (172)connects non-volatile data storage to the computer (152) in the form ofdisk drive (170). Disk drive adapters useful in computer systems thatsupport thread-specific event management in a non-stop debuggingenvironment according to embodiments of the present invention includeIntegrated Drive Electronics (‘IDE’) adapters, Small Computer SystemInterface (‘SCSI’) adapters, and others as will occur to those of skillin the art. Non-volatile computer memory also may be implemented for asan optical disk drive, electrically erasable programmable read-onlymemory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, aswill occur to those of skill in the art.

The example computer (152) of FIG. 1 includes one or more input/output(‘I/O’) adapters (178). I/O adapters implement user-orientedinput/output through, for example, software drivers and computerhardware for controlling output to display devices such as computerdisplay screens, as well as user (101) input from user input devices(181) such as keyboards and mice. The example computer (152) of FIG. 1includes a video adapter (209), which is an example of an I/O adapterspecially designed for graphic output to a display device (180) such asa display screen or computer monitor. Video adapter (209) is connectedto processor (156) through a high speed video bus (164), bus adapter(158), and the front side bus (162), which is also a high speed bus.

The exemplary computer (152) of FIG. 1 includes a communications adapter(167) for data communications with other computers (182) and for datacommunications with a data communications network (100). Such datacommunications may be carried out serially through RS-232 connections,through external buses such as a Universal Serial Bus (‘USB’), throughdata communications networks such as IP data communications networks,and in other ways as will occur to those of skill in the art.Communications adapters implement the hardware level of datacommunications through which one computer sends data communications toanother computer, directly or through a data communications network.Examples of communications adapters useful in computer systems thatsupport thread-specific event management in a non-stop debuggingenvironment according to embodiments of the present invention includemodems for wired dial-up communications, Ethernet (IEEE 802.3) adaptersfor wired data communications network communications, and 802.11adapters for wireless data communications network communications.

The arrangement of computers, networks, and other devices making up theexemplary system illustrated in FIG. 1 are for explanation, not forlimitation. Data processing systems useful according to variousembodiments of the present invention may include additional servers,routers, other devices, and peer-to-peer architectures, not shown inFIG. 1, as will occur to those of skill in the art. Networks in suchdata processing systems may support many data communications protocols,including for example TCP (Transmission Control Protocol), IP (InternetProtocol), HTTP (HyperText Transfer Protocol), WAP (Wireless AccessProtocol), HDTP (Handheld Device Transport Protocol), and others as willoccur to those of skill in the art. Various embodiments of the presentinvention may be implemented on a variety of hardware platforms inaddition to those illustrated in FIG. 1.

For further explanation, FIG. 2 sets forth an example non-stop debuggingGUI (124) presented to a user in accordance with embodiments of thepresent invention. The example GUI (124) of FIG. 2 provides an interfacefor a user to control operation of a debugger that supports non-stopdebugging. The debugger presenting the example GUI (124) of FIG. 2 isconfigured to debug a multi-threaded debuggee. That is, the debuggerpresenting the example GUI (124) of FIG. 2 and the multi-threadeddebuggee form a non-stop debugging environment.

The example GUI (124) of FIG. 2 includes a menu bar (208) that, in turn,includes a number of separate menus: a File menu, an Edit menu, a Viewmenu, a Non-Stop Options menu, and a Help menu. The Non-Stop Optionsmenu (206), when selected, may provide a user with various menu itemsthat support non-stop debugging.

The example GUI (124) of FIG. 2 also includes several independentportions—called panes (as in ‘window panes’) for clarity ofexplanation—a project pane (202), a source code pane (210), and twoseparate data panes (204, 212). Project pane (202) presents the filesand resources available in a particular software development project.Source code pane (210) presents the source code of the multi-threadeddebuggee. The data panes (204, 212) present various data useful indebugging the source code. In the example of FIG. 2, data pane (204)includes four tabs, each of which presents different data: a call stacktab (214), a register tab (214), a memory tab (218), and a thread tab(230). Data pane (212) includes four tabs: a watch list tab (220), abreakpoints (222) tab, a local variable tab (224), and a global variabletab (226).

The GUI (124) of FIG. 2 may support thread-specific event management inaccordance with embodiments of the present invention. For example, thebreakpoints tab (222) depicted in pan (212) sets forth threebreakpoints, one of which is a thread-specific breakpoint. The GUI (124)depicts breakpoints at line 23, line 102, and line 108. The breakpointat line 23 is associated with a thread having a thread identifier of‘4.’ When a thread having an identifier other than ‘4’ encounters thebreakpoint the debugger presenting the example GUI of FIG. 2 willimmediately resume execution of the thread, likely without notifying theuser. Although the resumption of execution may be quick, readers willrecognize that any stoppage of thread execution reduces performance ofthe debuggee.

Also, the thread tab (230) of the pane (204) in the example GUI (124) ofFIG. 2 depicts a listing of threads and each thread's present status.For example, the thread tab (230) depicts a thread having an identifierof ‘1’ as presently running and a thread having an identifier of ‘4’ ashalted upon encountering a breakpoint at line 25. The debuggerpresenting the example GUI (124) of FIG. 2 may operate forthread-specific event management by identifying, for the thread ofexecution not currently executing (thread ID=‘4’), a thread-specificevent associated with the thread (breakpoint at line 23) and removingthe thread-specific event for all threads of the debuggee. Said anotherway, once the thread 4 stops executing, the debugger removes thebreakpoint at line 23—a breakpoint associated only with thread 4—fromall threads, and no thread can encounter the breakpoint. In this way,the debugger reduces performance degradation.

In some embodiments, the user may selectively stop execution of a threador remove thread-specific events from a non-executing thread. In the GUI(124) of FIG. 2, for example, a user may select a thread in the threadtab (230), and select, from a drop-down selection list, an option tostop the selected thread's execution or remove thread-specificbreakpoints associated with the selected thread. In the example of FIG.2, the user has selected the thread having an identifier of 1 and ispresented an option to stop execution of the thread. The option toremove the thread's thread-specific breakpoints, however, is disabled asthe thread is currently executing. Once execution of the thread isstopped, however, the user may opt to remove thread-specific breakpointsfrom all threads.

The GUI items, menus, window panes, tabs, and so on depicted in theexample client-specific GUI (124) of FIG. 2, are for explanation, notfor limitation. Other GUI items, menu bar menus, drop-down menus,list-boxes, window panes, tabs, and so on as will occur to readers ofskill in the art may be included in client-specific GUIs presented bydebug clients in a distributed system in which collaborative softwaredebugging is carried out in accordance with embodiments of the presentinvention.

For further explanation, FIG. 3 sets forth a flow chart illustrating anexemplary method for thread-specific event management in a non-stopdebugging environment according to embodiments of the present invention.The method of FIG. 3 is carried out in a non-stop debugging environmentthat includes a debugger (126) configured to debug a debuggee. Thedebuggee includes a plurality of threads (122) of execution. In thenon-stop debugging environment, encountering an event by one of thethreads stops execution of only the one thread without concurrentlystopping execution of the other threads.

The method of FIG. 3 also includes identifying (302), by the debugger(126) for a thread (312) of execution of the debuggee not currentlyexecuting, a thread-specific event (130) associated with the thread(312). Identifying (302) a thread-specific event (130) associated withthe thread (312) may be carried out in various ways including, forexample, by searching a table of thread specific events maintained bythe debugger for any records containing events associated with thethread's (312) identifier.

The method of FIG. 3 also includes removing (306), by the debugger(126), the thread-specific event (130) for all threads (122) of thedebuggee. Removing the thread-specific event may be carried out byreplacing, at the memory location of the event, the original operationalcode (opcode). Breakpoints, for example, may be inserted into sourcecode by replacing an original opcode of a computer program instructionat a memory location of the thread's source code with another predefinedopcode that, when executed, creates an exception or interrupt handled bythe debugger. The original opcode, during this replacement, is stored ata predefined location so that the opcode may be replaced at the memorylocation if the breakpoint is disabled. Removing the thread-specificevent, therefore, may be carried out by replacing the predefined opcodewith the original opcode.

Upon the thread (31) resuming (310) execution, the method of FIG. 3continues by replacing (308), by the debugger, the thread-specific event(130). Replacing (308) the thread-specific event (130) may be carriedout by replacing the original opcode at the memory location in sourcecode of each thread with the predefined opcode that when executed causesan exception or interrupt handled by the debugger.

For further explanation, FIG. 4 sets forth a flow chart illustrating afurther exemplary method for thread-specific event management in anon-stop debugging environment according to embodiments of the presentinvention. The method of FIG. 4 is similar to the method of FIG. 3 inthat the method of FIG. 4 is carried out in a non-stop debuggingenvironment that includes a debugger (126) configured to debug amulti-threaded (122) debuggee, where the debugger (126) identifies (302)for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 4 differs from the method of FIG. 3, however, in thatthe method of FIG. 4 includes tracking (402) a length of time (404) thethread (312) is not executing. In the method of FIG. 4, removing (306)the thread-specific event is carried out by removing (408) thethread-specific event (310) only if the length of time (404) exceeds apredetermined threshold (406). In this way, a debugger may be configuredto reduce impact of encountering thread-specific events by threads otherthan the thread associated with the thread-specific event, not on everystop of a thread, but rather when the thread is stopped for somethreshold amount of time. This configuration may insure thatthread-specific event removals are performed only when beneficial toreducing the impact caused non-essential thread-specific eventencounters.

For further explanation, FIG. 5 sets forth a flow chart illustrating afurther exemplary method for thread-specific event management in anon-stop debugging environment according to embodiments of the presentinvention. The method of FIG. 5 is similar to the method of FIG. 3 inthat the method of FIG. 5 is carried out in a non-stop debuggingenvironment that includes a debugger (126) configured to debug amulti-threaded (122) debuggee, where the debugger (126) identifies (302)for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 5 differs from the method of FIG. 3, however, in thatthe method of FIG. 5 includes tracking (502) a number (504 of encountersof the thread-specific event (130) while the thread (312) is notexecuting. In the method of FIG. 5, removing (306) the thread-specificevent (130) for all threads of the debuggee is carried out by removing(508) the thread-specific event (130) for all threads (122) only if thenumber (504) of encounters exceeds a predetermined threshold (508). Inthis way, the debugger may be configured to allow a predefine number ofencounters before removing the thread-specific event. Again, like themethod of FIG. 4, the method of FIG. 5 enables the debugger to reducethe impact of non-essential thread-specific event encounters only whenbeneficial to do so—when the number of actual encounters represents anundesirable impact.

As mentioned above, a thread may stop execution for various reasons. Forfurther explanation, therefore, FIG. 6 sets forth a flow chartillustrating a further exemplary method for thread-specific eventmanagement in a non-stop debugging environment according to embodimentsof the present invention in which the execution of a thread is stoppedat the behest of a user. The method of FIG. 6 is similar to the methodof FIG. 3 in that the method of FIG. 6 is carried out in a non-stopdebugging environment that includes a debugger (126) configured to debuga multi-threaded (122) debuggee, where the debugger (126) identifies(302) for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 6 differs from the method of FIG. 3, however, in thatthe method of FIG. 6 also includes receiving (602) a user request tohold the thread (312) from executing and stopping (604) execution of thethread. A user may request to hold the thread from executing in variousways including, for example, via interaction with a GUI presented by thedebugger (126). Consider, for example, the GUI (124) in the example ofFIG. 2 in which a user is presented an option in a drop-down selectionlist to stop a thread from executing.

FIG. 7 presents another example in which a thread's execution isstopped. For further explanation, FIG. 7 sets forth a flow chartillustrating a further exemplary method for thread-specific eventmanagement in a non-stop debugging environment according to embodimentsof the present invention in which execution of a thread is stopped uponencountering an event. The method of FIG. 7 is similar to the method ofFIG. 3 in that the method of FIG. 7 is carried out in a non-stopdebugging environment that includes a debugger (126) configured to debuga multi-threaded (122) debuggee, where the debugger (126) identifies(302) for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 7 differs from the method of FIG. 3, however, in thatthe method of FIG. 7 includes encountering (702), by the thread (312),an event stopping execution of the thread. The event encountered by thethread (312) may be a thread-specific event or any event. Readers willrecognize that the benefit of removing a thread-specific eventassociated with the thread (312) from all threads (122) may be realizedwithout regard to the nature of the event encountered by the stoppedthread (312).

For further explanation, FIG. 8 sets forth a flow chart illustrating afurther exemplary method for thread-specific event management in anon-stop debugging environment according to embodiments of the presentinvention. The method of FIG. 8 is similar to the method of FIG. 3 inthat the method of FIG. 8 is carried out in a non-stop debuggingenvironment that includes a debugger (126) configured to debug amulti-threaded (122) debuggee, where the debugger (126) identifies (302)for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 8 differs from the method of FIG. 3, however, in thatthe method of FIG. 8 also includes determining (802) that the thread isin a wait state and, thereby, not currently executing. In the method ofFIG. 8, the thread (312) is considered to be ‘not currently executing’although no mechanism may be actively stopping execution of the thread.Consider, by contrast, a breakpoint that causes an interrupt of thethread's execution that is handled by the debugger (126). With such abreakpoint encounter, the thread is actively held from executing untilthe debugger causes the thread to resume execution. While in a waitstate, however, the thread is not actively held from execution, butrather the thread is passively not executing. The thread may be in await state for various reasons including, for example, by waiting on alock, such as a mutex or a semaphore, to become available, waiting on anI/O request to complete, waiting on a predefined time slice or ‘quant’of time to complete so that execution continues, and so on as will occurto readers of skill in the art.

For further explanation, FIG. 9 sets forth a flow chart illustrating afurther exemplary method for thread-specific event management in anon-stop debugging environment according to embodiments of the presentinvention. The method of FIG. 9 is similar to the method of FIG. 3 inthat the method of FIG. 9 is carried out in a non-stop debuggingenvironment that includes a debugger (126) configured to debug amulti-threaded (122) debuggee, where the debugger (126) identifies (302)for a thread (312) of execution not currently executing athread-specific event (130) associated with the thread (312); removes(306) the thread-specific event for all threads (122), and, upon thethread resuming (310) execution, replaces (308) the thread-specificevent (130).

The method of FIG. 9 differs from the method of FIG. 3, however, in thatthe method of FIG. 9 includes receiving (902), by the debugger (126)from an operating system (156), an indication that the thread (312) iswaiting for a lock restricting access to a resource and stopping (908),by the debugger (126), execution of the thread. A lock as the term isused here refers to an operating system supported lock, such as a mutexor semaphore. The term ‘resource’ may refer to any resource—methods,object, variables, I/O devices, a data communications bus a processorregister, a memory location, and so on as will occur to readers of skillin the art. The debugger (126) may receive an indication (904) that thethread (312) is waiting for a lock in various ways including, byrequesting the status of the thread from the operating system or throughuse of ptrace-type calls into the operating system for following theoperation of the operating system process responsible for maintaining alock.

At a time after removing the thread-specific event for all threads ofthe debuggee, the method of FIG. 9 continues by receiving (910), by thedebugger from the operating system (156), an indication (906) that thelock is available to the thread and resuming (310), by the debugger(126), execution of the thread.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readabletransmission medium or a computer readable storage medium. A computerreadable storage medium may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer readable storage medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer readable transmission medium may include a propagated datasignal with computer readable program code embodied therein, forexample, in baseband or as part of a carrier wave. Such a propagatedsignal may take any of a variety of forms, including, but not limitedto, electro-magnetic, optical, or any suitable combination thereof. Acomputer readable transmission medium may be any computer readablemedium that is not a computer readable storage medium and that cancommunicate, propagate, or transport a program for use by or inconnection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

1. A method of thread-specific event management in a non-stop debuggingenvironment, the non-stop debugging environment comprising a debuggerconfigured to debug a debuggee comprising a plurality of threads ofexecution, wherein encountering an event by one of the threads stopexecution of only the one thread without concurrently stopping executionof the other threads, the method comprising: identifying, by thedebugger for a thread of execution of the debuggee not currentlyexecuting, a thread-specific event associated with the thread; removing,by the debugger, the thread-specific event for all threads of thedebuggee; and upon the thread resuming execution, replacing, by thedebugger, the thread-specific event.
 2. The method of claim 1 furthercomprising tracking a length of time the thread is not executing,wherein removing the thread-specific event for all threads of thedebuggee further comprises removing the thread-specific event for allthreads only if the length of time exceeds a predetermined threshold. 3.The method of claim 1 further comprising tracking a number of encountersof the thread-specific event while the thread is not executing, whereinremoving the thread-specific event for all threads of the debuggeefurther comprises removing the thread-specific event for all threadsonly if the number of encounters exceeds a predetermined threshold. 4.The method of claim 1, further comprising: receiving a user request tohold the thread from executing; and stopping execution of the thread. 5.The method of claim 1, further comprising encountering, by the thread,an event stopping execution of the thread.
 6. The method of claim 1,further comprising determining that the thread is in a wait state and,thereby, not currently executing.
 7. The method of claim 1 furthercomprising: receiving, by the debugger from an operating system, anindication that the thread is waiting for a lock restricting access to aresource; stopping, by the debugger, execution of the thread; at a timeafter removing the thread-specific event for all threads of thedebuggee: receiving, by the debugger from the operating system, anindication that the lock is available to the thread; and resuming, bythe debugger, execution of the thread. 8-21. (canceled)